# Hot-linking quotations
# User process (CRM)
Sales user:
- picks a quotation,
- chooses to use the quotation as template for a new one,
- modifies the new quotation,
- marks the "link to original GVV task" checkbox,
- clicks on "create".
This is almost identical to the standard quotation copy process with the addition of a "hot link" checkbox.
# Implementation: GVV entities
A new entity "GVVAuftragClone" assigns additional quotations to an existing GVV task.
# Entity GVVAuftragClone
DB Table: [Giffits-Extra].[dbo].[GVV_auftrag_clone]
| column | type | comment |
|---|---|---|
| auftrag_angebot_DocNum | int | quotation number |
| auftrag_id | int | points to [Giffits-Extra].[dbo].[GVV_auftrag].auftrag_id |
# Implementation: Cloning API
GVV features an API to perform quotation cloning,
http://musterb.local.giffits.de/tools/gvv/live/api/cloneQuotation.php,
which is documented here.
# Implementation: CRM (SALLY)
CRM uses the GVV cloning API throughout the process of quotation creation. It is called right after successful creation of the quotation in SBO.
If no GVV task was assigned to the original quotation the process displays a warning to the user.
# Broken separation of concern
CRM directly queries the database owned by GVV. In terms of quotation cloning this affects gathering GVV task information for a quotation and assembling the according GVV link.
The current solution uses the same approach and just extends the existing SQL.
# Implementation: OA
The shop side of the OA solution remains unchanged: It uses the auth service to fetch possible proof images from a backend controller.
This backend controller is located inside legacymusterbtools at
~/tools/mygiffits/live/myGiffitsZugriffe.php, function
getStandbilder.
The backend function assembles the image files from the original location; No files have to be copied or renamed.